Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FYST-1812 make email case insensitive for pya #5600

Conversation

DrewProebstel
Copy link
Contributor

Link to pivotal/JIRA issue

Is PM acceptance required? (delete one)

  • Yes - don't merge until JIRA issue is accepted!

Reminder: merge main into this branch and get green tests before merging to main

What was done?

  • Makes sure the PYA flow is case insensitive for Email

How to test?

  • Try some capitalized and lowercase emails.

Copy link

Heroku app: https://gyr-review-app-5600-dca5b21a3cb7.herokuapp.com/
View logs: heroku logs --app gyr-review-app-5600 (optionally add --tail)

@DrewProebstel DrewProebstel changed the title make email case insensitive for pya FYST-1812 make email case insensitive for pya Feb 19, 2025
@@ -10,7 +10,7 @@ def update
@form = EmailAddressForm.new(email_address_form_params)

if @form.valid?
archived_intake = StateFileArchivedIntake.find_by(email_address: @form.email_address)
archived_intake = StateFileArchivedIntake.where("email_address ILIKE ?", @form.email_address).first
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[dust] it would be nice to be consistent with how we query both here and in the archived intake controller. either is fine, but ILIKE is a bit more esoteric, so i slightly prefer using lower for clarity

@DrewProebstel DrewProebstel merged commit 594b9cf into main Feb 20, 2025
7 checks passed
@DrewProebstel DrewProebstel deleted the FYST-1812-state-file-archived-intake-request-state-file-archived-intake-lookup-relies-on-matching-exact-email-instead-of-possible-capitalization-combinations branch February 20, 2025 23:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants